-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(color-contrast, utils): add more options to color-contrast, add utils.deepMerge, deprecate commons.color.hasValidContrastRatio #2256
Conversation
…ast ratio requirements
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put in a suggestion, let me know what you think.
With nested options, the |
lib/checks/color/color-contrast.json
Outdated
"normal": { | ||
"expected": 4.5, | ||
"minThreshold": 0, | ||
"maxThreshold": 999 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This number is arbitrary. It just needed to be something larger than the contrast ratio could ever go (#fff vs #000 = 21:1)
Co-authored-by: Wilco Fiers <[email protected]>
Co-authored-by: Wilco Fiers <[email protected]>
Co-authored-by: Wilco Fiers <[email protected]>
Co-authored-by: Wilco Fiers <[email protected]>
Co-authored-by: Wilco Fiers <[email protected]>
Co-authored-by: Wilco Fiers <[email protected]>
We needed to have options to specify the minimum contrast the check should apply to allow rules a specific range of contrast to determine pass/fail.
Closes issue: #2175
Reviewer checks
Required fields, to be filled out by PR reviewer(s)